feat(structure): History UI updates #7462
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
No changes to documentation |
|
Component Testing Report Updated Nov 19, 2024 5:55 PM (UTC) ❌ Failed Tests (1) -- expand for details
|
pedrobonamin
force-pushed
the
history-updates
branch
from
4b07286
to
39792f5
Compare
pedrobonamin
force-pushed
the
history-updates
branch
from
39792f5
to
17e81d0
Compare
pedrobonamin
force-pushed
the
history-updates
branch
from
17e81d0
to
264022e
Compare
* feat(sanity): update restore button * chore(sanity): update translations * feat(sanity): add left side information on footer (revision status line)
…el (#7435) * feat(structure): add history and review tabs to changes inspector panel * fix(structure): move changes inspector navigation to paneRouter * fix(structure): update isReviewChangesOpen check in ChangeConnectorRoot * fix(structure): rename uses of version to revision * chore(core): rename review changes action to history
…nks (#7449) * feat(structure): update TimelineItem to match new UI, prepare for chunks * chore(core): export getCalendarLabels to support DateTimeInput reusability
* feat(structure): add squashed chunks to timeline * feat(structure): refactor expandable item, all items need to be rendered in the same virtual list * feat(structure): expand elements on menu click * chore(structure): clean timeline item
…ed during render
pedrobonamin
force-pushed
the
history-updates
branch
from
d983b67
to
fa27a83
Compare
juice49
pushed a commit
that referenced
this pull request
Nov 22, 2024
Merge draft changes into the publish action. Moves revision into the history panel Co-authored-by: RitaDias <[email protected]>
bjoerge
added a commit
that referenced
this pull request
Nov 26, 2024
* next: (37 commits) v3.65.0 fix(deps): update dependency @sanity/insert-menu to v1.0.13 (#7880) fix(deps): update dependency @sanity/presentation to v1.18.5 (#7881) fix(deps): Update dev-non-major (#7875) fix(deps): update dependency @sanity/ui to ^2.8.25 (#7876) fix(telemetry): log (well known) workspace and dataset names (#7859) fix(deps): update dependency @portabletext/editor to ^1.11.3 (#7865) fix(deps): update dependency react-rx to ^4.1.7 (#7874) chore(deps): dedupe pnpm-lock.yaml (#7873) chore(ci): max react compiler warnings are now 79 fix(deps): update React Compiler dependencies 🤖 ✨ (#7872) fix(core): discard announcements dialog onClickOutside (#7863) feat(structure): History UI updates (#7462) chore(cli): temporarily disable telemetry tests (#7845) chore(deps): update dependency turbo to ^2.3.0 (#7846) chore(lockfile): update dependency @sanity/asset-utils to v2.2.0 (#7847) chore(lockfile): update dependency react-focus-lock to v2.13.2 (#7848) feat: add support for React Compiler beta (#7702) v3.64.3 fix(deps): update dependency @portabletext/editor to ^1.11.1 (#7861) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces UI changes into the
historyandrevisionpanel.What does "chunks are squashed together on publish" means?
Once the draft changes are published all the draft edits done before that publish will be squashed and shown as 1 change, that could be expanded, showing also the collaborators for that published.
This means:
If we have the following mutations:
[draftEdit, publish, draftEdit, draftEdit, create]it will be shown as
[draftEdit, publish (expandable), create]On expand, it will show the two collapsed draftEdit actions
The changes are not removed from the history, they are only visually squashed for easier navigation in the UI.
This is achieved by creating a relation between parents publish action and children draftEdit actions, in the addChunksMetadata function.
Collapsable.history.items.mov
What to review
Are the changes correct? Is something missing?
Testing
Notes for release
Updates to history inspector UI, edits are now collapsed into the Published Event. From and To revision selectors are added into the inspector.